Use router instead of internal component state #61
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the
BlogPostFlow
component was handling transitions between screens internally, instead of relying on the URL to drive navigation.This PR fixes that by removing this component in favor of two others, which are mapped to two different URLs:
NewBlogPost
:/session/${ sessionId }/flow/blog-post/new
EditBlogPost
:/session/${ sessionId }/flow/blog-post/${ postId }
This makes the app behave in more standard "CRUD" way.
Additionally, some other small changes were made:
window.trywp.navigateTo( '/start/home' )
Toolbar
component for rendering the buttons of each screen (see screen capture below), so that the "next" button is always on the top right.Screen captures